⚠️ Jira Issue Key Missing

Your PR title doesn't contain a Jira issue key. Consider adding it for better traceability.

Example:

• feat: add user authentication (CM-123)
• feat: add user authentication (IN-123)

Projects:

• CM: Community Data Platform
• IN: Insights

Please add a Jira issue key to your PR title.

PR Summary

Low Risk
Single cron timing change with no SQL or schema edits; worst case is briefly different freshness or load timing for members_sorted consumers.

Overview
Shifts when the members_sorted copy pipe runs each hour by updating COPY_SCHEDULE from 8 * * * * to 36 * * * * in members_sorted_copy_pipe.pipe. The pipe logic and target datasource are unchanged; only the cron minute moves later in the hour.

That table is upstream of activity-relations enrichment (valid-member filtering via memberId IN (SELECT id FROM members_sorted)), so the change is meant to stagger this refresh relative to other hourly Tinybird copy jobs rather than change what gets built.

^{Reviewed by Cursor Bugbot for commit 6a3ff1c. Bugbot is set up for automated code reviews on this repo. Configure here.}

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ gaspergrom
❌ epipav
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

lgtm